home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
keyb
/
keydef03.zip
/
KEYDEF.MSG
< prev
next >
Wrap
Text File
|
1993-02-08
|
14KB
|
322 lines
----------------------------------------------------------------------
Date: 1 Jun 90 09:13:00 CST
From: "MBIAN::PERRY" <perry%mbian.decnet@beach.gal.utexas.edu>
Subject: ANSI.SYS questions
I am devising a menu system to be used by the secretaries in my
department. I am using ANSI.SYS to pre-define strings within the
function keys to call the appropriate batch file. I'm sure every one of
you knows the drill.
The problem I am having is that this method works for 95% of the
applications. I have prepared a secondary file to reset the function
keys to their initial values. Even after this is done, some of the
applications act strangely as if the function keys were still defined
to some value other than their original value. It appears as though
just by virtue of defining the function keys with ANSI.SYS at all, some
flag somewhere is corrupted and the keys are not being restored to
their boot-up default value.
Is there any way the function keys can be TRULY reset to their initial
values? The applications that exhibit this strange behavior are
SIGMAPLOT and SLIDE WRITER PLUS. Any information would be helpful.
Thank you in advance.
John Perry - KG5RG
University of Texas Medical Branch
The Marine Biomedical Institute
200 University Blvd. H-43
Galveston, Texas 77550-2772
Voice : (409) 761-2124
FAX : (409) 762-9382
You can send mail to me at any of the following addresses:
DECnet : MBIAN::PERRY
THEnet : MBIAN::PERRY
Internet : perry%mbian.decnet@beach.gal.utexas.edu
SPAN : UTSPAN::UTADNX::MBIAN::PERRY
------------------------------
Date: Mon, 25 Jun 90 10:10 MET
From: "Jim Groeneveld, NIPG TNO." <GROENEVELD%TNO.NL@CUNYVM.CUNY.EDU>
Subject: ANSI.SYS questions
Dear John Perry,
The problem with keyboard redefinition with ANSI.SYS is that the total
amount of the redefinitions may only be a limited number of bytes, 192
I believe. I don't know whether the keys to be redefined add to that
number themselves. But if you have a set of definitions (in a file to
be TYPEd to CON, the screen) and you want to reset the keys to their
original values by defining them as themselves, these (re)definitions
add to the total amount even if already redefined keys are redefined
again. The old redefinitions still take space in memory, they are not
removed, though they are not active anymore.
Now, if by the second set of redefinitions the total amount of bytes
used in all redefinitions exceeds the limitation of 192 bytes problems
may arise such as that the new redefinitions may not be active, leaving
the old ones active. I presume this might be the problem you are
encountering.
This also means that it is not possible to define and redefine keys
unlimitedly as desired. In general it is only possible to use a set of
definitions up to the mentioned limit of bytes and have those
definitions active during a whole session without deactivating or
removing them.
I hope this helps you.
Regards - Jim Groeneveld.
P.S. I have a (BASIC) program with which one may easily setup a file
with keyboard assignments/redefinitions. If you are interested, drop me
a line.
+-----------------------------------------------------------------------------+
| NIPG TNO <work>: Y. Groeneveld (call name: Jim) <home>| GROENEVELD@TNO.NL |
| Postbus 124 | Wassenaarseweg 56 | Schoolweg 14 | GROENEVELD@HDETNO51 |
| 2300 AC Leiden | 2333 AL Leiden | 8071 BC Nunspeet | TNOSUR::GROENEVELD |
| Nederland (NL) : (+31|0)71-178810 | (+31|0)3412-60413| RULTNO::JIM |
+-----------------------------------------------------------------------------+
------------------------------
Date: Mon, 25 Jun 90 17:00:34 MET
From: Ben Salemans <U070011%HNYKUN11.BITNET@CUNYVM.CUNY.EDU>
Subject: Conflicting 'prompt' and 'echo off' commands in BAT-file
Hi there,
I have developed the following BAT-file (PGUPPGDN.BAT):
*----------------------------*
| prompt $e[0;73;"PgUp";13p |
| prompt $e[0;81;"PgDn";13p |
| set prompt= |
*----------------------------*
After the execution of this PGUPPGDN.BAT-file, the pushing of the PgUp-
or PgDn-key results in the display of the word 'PgUp' or 'PgDn' on the
screen AND the execution of the PgUp- or PgDn-command, which I have
defined in resp. the PgUp- and PgDn-BAT-files. In the appendix to this
mail you'll find the documented version of this BAT-file. As you can
see, I use the DOS-prompt command to define these key-strokes.
Because I did not want to display the contents of the PGUPPGDN.BAT file
while executing, I simply added the usual 'echo off' line at the top of
the file.
*----------------------------*
| echo off |
| prompt $e[0;73;"PgUp";13p |
| prompt $e[0;81;"PgDn";13p |
| set prompt= |
*----------------------------*
But after adding the 'echo off'-line the BAT-file did not execute well!
I would like to know if any of the IBMPC-L-readers recognizes this
problem and knows how to solve it. I have the impression that the
prompt-command feels the urge to display something on the screen. When
this is impossible (by the 'echo off'-line) the command does not work.
[As you may know, it is next to impossible, if not impossible, to send
the <esc> character (chr$(27)) from the command line to ANSI.SYS. When
DOS sees $e in the PROMPT command, it sends ESC to ANSI.SYS. If echo
is OFF, nothing is echoed to the screen, including the ESC character,
so nothing reaches ANSI.SYS... If you want to use ANSI.SYS to
re-program your keyboard, you'll have to leave echo ON until you finish
re-defining your keys. gph]
Bye!
Ben Salemans (u070011@hnykun11)
APPENDIX: PGUPPGDN.BAT with annotations in REM-statements
=========================================================
REM Ben Salemans, 22-VI-1990
REM --Start-of-definition-of-PgUp-Key-by-using-the-prompt-command------->
REM Pushing the PgUp-Key will result in the display of the string "PgUp"
REM on the screen and the execution of PgUp as a command.
REM Nota bene: '73' is the ASCII-code for the PgUp-key; 13p represents
REM a strike on the Enter-key.
prompt $e[0;73;"PgUp";13p
REM <------End-of-definition-of-PgUp-Key---------------------------------
REM =====================================================================
REM --Start-of-definition-of-PgDn-Key-by-using-the-prompt-command------->
REM Pushing the PgDn-Key will result in the display of the string "PgDn"
REM on the screen and the execution of PgDn as a command.
REM Nota bene: '81' is the ASCII-code for the PgDn-key; 13p represents
REM a strike on the Enter-key.
prompt $e[0;81;"PgDn";13p
REM <------End-of-definition-of-PgDn-Key---------------------------------
REM =====================================================================
REM Now we must set the prompt (else there won't be any prompt on the
REM screen)
set prompt=
------------------------------
Date: Fri, 20 Jul 90 11:47 MET
From: "Jim Groeneveld, NIPG TNO." <GROENEVELD%TNO.NL@CUNYVM.CUNY.EDU>
Subject: Conflicting 'prompt' and 'echo off' commands in BAT-file
Dear Ben <U070011@HNYKUN11>,
{ I write this reply to you in English instead of Dutch, because I also
will send it to the IBMPC-L digest for general interest. }
With regard to your problem concerning "conflicting 'prompt' and 'echo
off' commands in BAT-file" I have the following remarks:
1. Gregory Hicks is right stating within your message that ECHO should
be ON to activate the temporary prompts by displaying them on the
screen. (Nothing will appear on the screen, however, because the
definitions do not show; they only are 'remembered' when sent to the
screen.)
2. Within your Bat-file you could have ECHO ON just before the PROMPTs
and ECHO OFF right after them.
3. At the end you empty the environment string PROMPT giving